Skip to content

fix(core): surface API error detail and the failing endpoint URL#1619

Merged
mergify[bot] merged 2 commits into
mainfrom
devs/JulianMaurin/fix/stack-push-output/surface-api-error-detail-failing-endpoint-url--76d98c2d
Jun 18, 2026
Merged

fix(core): surface API error detail and the failing endpoint URL#1619
mergify[bot] merged 2 commits into
mainfrom
devs/JulianMaurin/fix/stack-push-output/surface-api-error-detail-failing-endpoint-url--76d98c2d

Conversation

@JulianMaurin

Copy link
Copy Markdown
Contributor

HTTP error rendering dumped the raw response body — so a Mergify API {"detail": "..."} envelope reached the user verbatim — and never showed which URL failed. Extract the JSON detail field when present (falling back to the raw body), and append a trailing url: line on HTTP errors plus the contacted URL on network/timeout errors, matching the Python check_for_status output.

Co-Authored-By: Claude Opus 4.8 (1M context) noreply@anthropic.com

Depends-On: #1618

@JulianMaurin

JulianMaurin commented Jun 16, 2026

Copy link
Copy Markdown
Contributor Author

This pull request is part of a Mergify stack:

# Pull Request Link
1 fix(stack): restore prefix-match error detail and not-found exit codes #1618
2 fix(core): surface API error detail and the failing endpoint URL #1619 👈
3 fix(ci,queue,stack): restore minor output details lost in the port #1620
4 fix(stack): reapply cherry-picks when dropping merged commits during sync #1630
5 feat(stack): stream push progress with live in-place rows #1633

@mergify

mergify Bot commented Jun 16, 2026

Copy link
Copy Markdown
Contributor

Merge Protections

🟢 All 6 merge protections satisfied — ready to merge.

@mergify mergify Bot requested a review from a team June 16, 2026 22:02
@JulianMaurin JulianMaurin marked this pull request as ready for review June 17, 2026 07:28
@JulianMaurin JulianMaurin force-pushed the devs/JulianMaurin/fix/stack-push-output/surface-api-error-detail-failing-endpoint-url--76d98c2d branch from 643363e to 4396d07 Compare June 17, 2026 17:44
@JulianMaurin JulianMaurin force-pushed the devs/JulianMaurin/fix/stack-push-output/restore-prefix-match-error-detail-found-exit-codes--52793895 branch from 266f9bb to 2675a1a Compare June 17, 2026 17:44
@JulianMaurin

JulianMaurin commented Jun 17, 2026

Copy link
Copy Markdown
Contributor Author

Revision history

# Type Changes Reason Date
1 initial 643363e 2026-06-17 17:44 UTC
2 rebase 643363e → 4396d07 (rebase only) 2026-06-17 17:44 UTC
3 rebase 4396d07 → e403d28 (rebase only) 2026-06-18 07:26 UTC

JulianMaurin and others added 2 commits June 18, 2026 09:26
Ambiguous <COMMIT> resolution lost the "ambiguous" wording, the match count, each candidate's Change-Id, and used a 7-char SHA instead of 12. A no-match note target returned InvalidState (exit 7) instead of StackNotFound (3), and `stack open` on an empty stack exited 0 instead of 3, breaking $?-based detection. Add a shared match_commit helper (one copy of the Python reorder.py wording) used by drop/squash/fixup/edit/move/reword/reorder/note, and fix the two exit codes.

Also restore the remediation guidance Python printed: the `targets itself` error (sync/push/list) regains the remote URL and both `git branch` fix commands, and the trunk-not-resolvable error regains the concrete `--set-upstream-to` hint.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Change-Id: I527938955f9a8b683f5c172d330a9faaea4517d5
HTTP error rendering dumped the raw response body — so a Mergify API `{"detail": "..."}` envelope reached the user verbatim — and never showed which URL failed. Extract the JSON `detail` field when present (falling back to the raw body), and append a trailing `url:` line on HTTP errors plus the contacted URL on network/timeout errors, matching the Python check_for_status output.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Change-Id: I76d98c2d9a91d6ba5ad1747c91c56d4e1ade869f
@JulianMaurin JulianMaurin force-pushed the devs/JulianMaurin/fix/stack-push-output/surface-api-error-detail-failing-endpoint-url--76d98c2d branch from 4396d07 to e403d28 Compare June 18, 2026 07:26
@JulianMaurin JulianMaurin force-pushed the devs/JulianMaurin/fix/stack-push-output/restore-prefix-match-error-detail-found-exit-codes--52793895 branch from 2675a1a to 6885975 Compare June 18, 2026 07:26
@mergify mergify Bot deployed to Mergify Merge Protections June 18, 2026 07:27 Active
Base automatically changed from devs/JulianMaurin/fix/stack-push-output/restore-prefix-match-error-detail-found-exit-codes--52793895 to main June 18, 2026 07:59
@mergify mergify Bot requested a review from a team June 18, 2026 08:10
@mergify

mergify Bot commented Jun 18, 2026

Copy link
Copy Markdown
Contributor

Queued — the merge queue status continues in this comment ↓.

@mergify

mergify Bot commented Jun 18, 2026

Copy link
Copy Markdown
Contributor

Merge Queue Status

This pull request spent 10 minutes 21 seconds in the queue, including 7 minutes 10 seconds running CI.

Required conditions to merge

mergify Bot added a commit that referenced this pull request Jun 18, 2026
@mergify mergify Bot added the queued label Jun 18, 2026
@mergify mergify Bot merged commit fa23605 into main Jun 18, 2026
36 checks passed
@mergify mergify Bot deleted the devs/JulianMaurin/fix/stack-push-output/surface-api-error-detail-failing-endpoint-url--76d98c2d branch June 18, 2026 08:39
@mergify mergify Bot removed the queued label Jun 18, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

3 participants